-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Improve wording on transactional methods inherited from SimpleJpaRepository
and repository fragments
#2207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve wording on transactional methods inherited from SimpleJpaRepository
and repository fragments
#2207
Conversation
Actually, methods on |
Yes. You give measlead answer as documentation. That's a problem. Does your answer follow that |
Therefore your observation is correct. Note that transactional attributes defined on |
Yes, but doc says about [all] CRUD methods of repository
This part may be clarified by this PR. |
This PR addresses only a subset, so my intent is rather to mention both interfaces to document the exact behavior to expect. |
Ok, will you make it yourself or my help required? |
I can take it if you don't mind. |
Ok, but I want to to check if explanation will be clean. |
SimpleJpaRepository
and repository fragments
…sitory and repository fragments. Closes #2207
…sitory and repository fragments. Closes #2207
…sitory and repository fragments. Closes #2207
…sitory and repository fragments. Closes #2207
…sitory and repository fragments. Closes #2207
Transactionality documentation sectional may mislead about apply
@Transactional
for custom repository, which extendsJpaRepository
(proof).Spring JPA JavaDoc may be clarified by this PR.
Tests:
I test
method call with property
When no
@Transactional
on class or method, transaction for custom method is not createdWith annotation on class or method level transaction is created